Sensitive drug distribution systems and methods

ABSTRACT

A drug distribution system and method utilizes a central pharmacy and database to track all prescriptions for a sensitive drug. Information is kept in the database regarding all physicians allowed to prescribe the sensitive drug, and all patients receiving the drug. Abuses are identified by monitoring data in the database for prescription patterns by physicians and prescriptions obtained by patients and/or caregivers. Further verification is made that the physician is eligible to prescribe the drug by consulting a separate database, and optionally whether any actions are taken against the physician. Multiple controls beyond those for normal drugs are imposed on the distribution depending on the sensitivity of the drug.

RELATED APPLICATIONS

This application is a divisional of and claims priority to U.S. application Ser. No. 16/032,501, filed on Jul. 11, 2018, which claims priority to U.S. Provisional Application No. 62/534,892, filed on Jul. 20, 2017, and claims priority to U.S. Provisional Application No. 62/607,221, filed on Dec. 18, 2017, both of which are related to U.S. Serial application Ser. No. 14/196,603, filed on Mar. 4, 2014, which is a Continuation of and claims priority to U.S. Serial application Ser. No. 13/592,202, filed on Aug. 22, 2012 and issued on May 20, 2014 as U.S. Pat. No. 8,731,963, which is a Continuation of and claims priority to U.S. Serial application Ser. No. 13/013,680, filed on Jan. 25, 2011, which is a Continuation of and claims priority to U.S. application Ser. No. 12/704,097, filed on Feb. 11, 2010 and issued on Feb. 22, 2011 as U.S. Pat. No. 7,895,059, which is a Continuation of and claims priority to U.S. application Ser. No. 10/322,348, filed on Dec. 17, 2002 and issued on Feb. 23, 2010 as U.S. Pat. No. 7,668,730, which applications are herein incorporated by reference in their entirety.

TECHNICAL FIELD

The technical field generally relates to the distribution of drugs, and in particular, to the distribution of sensitive drugs to pediatric patients. Additionally, an embodiment relates to using an exclusive pediatric database to monitor and control the distribution of sensitive drugs to pediatric patients.

BACKGROUND

Sensitive drugs are controlled to minimize risk and ensure that they are not abused, or cause adverse reactions. Such sensitive drugs are approved for specific uses by the Food and Drug Administration, and must be prescribed by a licensed physician in order to be purchased by consumers. Some drugs, such as cocaine and other common street drugs are the object of abuse and illegal schemes to distribute for profit. Some schemes include doctor shopping, diversion, and pharmacy thefts. A locked cabinet or safe is a requirement for distribution of some drugs.

Certain agents, such as gamma hydroxy buterate (MB) are also abused, yet also are effective for therapeutic purposes such as treatment of daytime cataplexy in patients with narcolepsy. Some patients however, will obtain prescriptions from multiple doctors, and have them filled at different pharmacies. Still further, an unscrupulous physician may actually write multiple prescriptions for a patient, or multiple patients, who use cash to pay for the drugs. These patients will then sell the drug to dealers or others for profit.

There is a need for a distribution system and method that directly addresses these abuses. There is a further need for such a system and method that provides education and limits the potential for such abuses.

SUMMARY

A drug distribution system and method utilizes a central pharmacy and database to track all prescriptions for a sensitive drug that is distributed to pediatric patients (or elderly or other special needs patients). Information is kept in a central database regarding all physicians allowed to prescribe the sensitive drug, all patients receiving the drug, and all caregivers associated with pediatric patients (or elderly or other special needs patients). Abuses are identified by monitoring data in the database for prescription patterns by physicians and prescriptions obtained by patients and/or caregivers. Further verification is made that the physician is eligible to prescribe the drug by consulting a separate database for a valid DEA license, and optionally state medical boards to determine whether any corrective or approved disciplinary actions relating to controlled substances have been brought against the physician. Multiple controls beyond those for traditional drugs are imposed on the distribution depending on the sensitivity of the drug.

Education is provided to the physician, patient, and caregiver. Prior to shipping the drug for the first time, the patient and caregiver are contacted to ensure that product- and abuse-related educational materials have been received and/or read. The patient and/or caregiver may provide the name of a designee to the central pharmacy who is authorized to accept shipment of the drug. Receipt of the initial drug shipment is confirmed by contacting the patient and/or caregiver. Either a phone call or other communication to the patient and/or caregiver within a set time after delivery may be made to ensure receipt. Further, a courier service's tracking system is used to confirm delivery in additional embodiments. If a shipment is lost, an investigation is launched to find it.

Prescription refills are permitted in the number specified in the original prescription. In addition, if a prescription refill is requested by the patient and/or caregiver prior to the anticipated due date, such refills will be questioned. A lost, stolen, destroyed or spilled prescription/supply is documented and replaced to the extent necessary to honor the prescription, and will also cause a review or full investigation.

An exclusive central database that is associated with the central pharmacy contains all relevant data related to distribution of the drug and the process of distributing it, including patient, caregiver, physician, and prescription information. Several queries and reports are run against the database to provide information which might reveal potential abuse of the sensitive drug, such as early refills.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a computer system for use in implementing a sensitive drug distribution system.

FIG. 2 is a flowchart describing a method for sensitive drug distribution at least partially utilizing a computer system such as that shown in FIG. 1.

FIG. 3 is a flowchart describing a method for sensitive drug distribution at least partially utilizing a computer system such as that shown in FIG. 1.

FIG. 4 is a block diagram of database fields.

FIG. 5 is a block diagram showing a list of queries against the database fields.

FIG. 6 is a copy of one example prescription and enrollment form.

FIG. 7 is a copy of one example of a NORD application request form for patient financial assistance.

FIG. 8 is a copy of one example voucher request for medication for use with the NORD application request form of FIG. 7.

FIG. 9 is a copy of certificate of medical need.

FIGS. 10A, 10B and 10C are descriptions of sample reports obtained by querying a central database having fields represented in FIG. 4.

FIGS. 11A, 11B, 11C, and 11D are a flowchart describing a method for sensitive drug distribution to a pediatric patient population at least partially utilizing a computer system such as that shown in FIG. 1.

FIGS. 12A and 12B are a flowchart describing a method for sensitive drug distribution to a pediatric population at least partially utilizing a computer system such as that shown in FIG. 1.

FIG. 13 is an example embodiment of an eBook.

DETAILED DESCRIPTION

In the following description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those of ordinary skill in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that structural, logical and electrical changes may be made without departing from the scope of the present invention. The following description is, therefore, not to be taken in a limited sense, and the scope of the present invention is defined by the appended claims.

The functions or algorithms described herein are implemented in software or a combination of software and human implemented procedures in one embodiment. The software comprises computer executable instructions stored on computer readable media such as memory or other types of storage devices. The term “computer readable media” is also used to represent carrier waves on which the software is transmitted. Further, such functions correspond to modules, which are software, hardware, firmware of any combination thereof. Multiple functions are performed in one or more modules as desired, and the embodiments described are merely examples. The software is executed on a digital signal processor, ASIC, microprocessor, or other type of processor operating on a computer system, such as a personal computer, server or other computer system.

A sensitive drug is one which can be abused, or has addiction properties or other properties that render the drug sensitive. One example of such a drug is sodium oxybate, also known as gamma hydroxy butyrate (GHB C₄H₇NaO₃), which is useful for treatment of cataplexy in patients with narcolepsy. GHB is marketed under the trademark of Xyrem® (sodium oxybate oral solution), which trademark can be used interchangeably with GHB herein. Sensitive drugs also include narcotics or other drugs which require controls on their distribution and use to monitor behaviors to prevent abuse and adverse side effects.

In one embodiment, Xyrem® is subject to a restricted distribution program. One aspect of the program is to educate physicians and patients about the risks and benefits of Xyrem®, including support via ongoing contact with patients and a toll free helpline. Initial prescriptions are filled only after a prescriber and patient have received and read the educational materials. Further, patient, caregiver (who is associated with a pediatric, elderly, or other special needs patient), and prescribing physician registries are maintained and monitored to ensure proper distribution.

In a further embodiment, bulk sodium oxybate is manufactured at a single site, as is the finished drug product. Following manufacture of the drug product, it is stored at a facility compliant with FDA Schedule III regulations, where a consignment inventory is maintained. The inventory is owned by a company, and is managed by a central pharmacy, which uses an exclusive central computer database and which maintains the consignment inventory. Xyrem® is distributed and dispensed through a primary and exclusive central pharmacy, which as noted uses an exclusive central database, and is not stocked in retail pharmacy outlets. It is distributed by overnight carriers, or by US mail in one embodiment to potentially invoke mail fraud laws if attempts of abuse occur.

FIG. 1 is a simplified block diagram of a computer system 100, such as a personal computer for implementing at least a portion of the methods described herein. A central processing unit (CPU) 110 executes computer programs stored on a memory 120. Memory 120 in one embodiment comprises one or more levels of cache as desired to speed execution of the program and access to data on which the programs operate. The CPU is directly coupled to memory 120 in one embodiment. Both CPU 110 and memory 120 are coupled to a bus 130. A storage 140, I/O 150 and communications 160 are also coupled to the bus 130. Storage 140 is usually a long term storage device, such as a disk drive, tape drive, DVD, CD or other type of storage device. In one embodiment, storage 140 is used to house a database for use with one or more embodiments of the present invention. I/O 150 comprises keyboards, sound devices, displays and other mechanisms by which a user interacts with the computer system 100. Communications 160 comprise a network, phone connection, local area network, wide area network or other mechanisms for communicating with external devices. Such external devices comprise servers, other peer computers and other devices. In one embodiment, such external device comprises a database server that is used in place of the database on storage 140. Other computer system architectures capable of executing software and interacting with a database and users may also be used. Appropriate security measures such as encryption are used to ensure confidentiality. Further, data integrity and backup measures are also used to prevent data loss.

In many instances, a sensitive drug, such as Xyrem®, must be distributed under an umbrella of a Risk Evaluation and Mitigation Strategy (REMS) program. A purpose of a REMS program is to mitigate the risks of serious adverse outcomes resulting from inappropriate prescribing, misuse, abuse, and/or diversion of the sensitive prescription drug, such as Xyrem®, which as noted above, is used for the treatment of cataplexy in patients with narcolepsy and for the treatment of excessive daytime sleepiness (EDS) in patients with narcolepsy. This goal is achieved by 1) informing prescribers, pharmacists, patients, and caregivers of the risks, contraindications, potential for abuse, misuse, and overdose, and the safe use, handling, and storage of the sensitive drug, and 2) ensuring that central pharmacy controls exist prior to filling prescriptions, wherein the controls screen for concomitant use of sedative hypnotics and other potentially interacting agents, monitor for inappropriate prescribing, and monitor and notify prescribers about concomitant use of contraindicated medications or signs of potential abuse, misuse, and/or diversion. One feature of such a REMS program is a single, certified, central pharmacy, and its associated exclusive computer database, that handles all prescription requests, written by all prescribers, for all patients being prescribed the sensitive drug. To become certified, all pharmacy staff and pharmacists of the central pharmacy must have completed a REMS pharmacy training program. The exclusive central database contains information about patient, caregiver, and prescriber enrollments, prescriptions for sensitive drugs, sensitive drug shipments, and Risk Management Reports (RMRs) generated by the certified, central pharmacy whenever there is activity raising a suspicion of abuse, misuse, and/or diversion, including requests for early refills.

All patients must be enrolled in the REMS program before they can receive a sensitive drug shipment. Additionally, as noted below in connection with FIG. 2, an enrolled prescriber completes an enrollment form for the patient and submits the form to the REMS program for processing and completion of enrollment. This form provides the patient's demographic and insurance information, links an enrolled prescriber to an enrolled patient, and verifies that specified requirements have been met, including an acknowledgment that the prescriber has counseled the patient on the serious risks and safe use of the sensitive drug. This information is entered into the exclusive database of the certified, central pharmacy, thereby allowing the pharmacy to verify that the patient is enrolled as part of its validation process prior to dispensing the sensitive drug. Additionally, all prescriptions for the sensitive drug go directly from an enrolled prescriber to the REMS Program, which limits an individual's ability to forge prescriptions or secure uncontrolled amounts of the sensitive drug with multiple prescriptions from different prescribers. As a further precaution, the sensitive drug prescription form is only available directly from the REMS program, not indirectly from the REMS website or other secondary source. The prescriber is notified once a patient is successfully enrolled and can be prescribed the sensitive drug.

Prescribers are considered to be enrolled in the REMS program only after verification that the prescriber enrollment form has been completed and the requirements described on the form have been met. Enrollment information is entered into the exclusive database of the certified, central pharmacy so that the pharmacy can verify that the prescriber is enrolled in the REMS program as part of its validation process prior to accepting a sensitive drug prescription or dispensing the sensitive drug. The certified, central pharmacy fills prescriptions only from prescribers who have completed enrollment in the REMS program. Prescribers are not enrolled (and therefore their patients cannot receive the sensitive drug) until the prescribers verify that they have reviewed educational materials and understand the approved indications and risks of the sensitive drug and complete the prescriber enrollment form. Upon receipt of an initial prescription, the certified, central pharmacy checks the exclusive database to ensure that the prescriber is enrolled. If the prescriber is enrolled, the certified, central pharmacy will verify the prescriber's name, DEA number, and state license number using appropriate sources. The DEA and license confirmation ensures that only prescriptions from enrolled prescribers who can legally prescribe a controlled substance are filled.

The certified, central pharmacy tracks each shipment of the sensitive drug through a carrier's or delivery service's website to confirm shipment within a particular time frame, such as one business day. Tracking reports are generated to confirm the receipt of orders shipped during the previous 48 hours. If an order is not delivered on the initial attempt, the carrier can make multiple attempts to redeliver. If redelivery attempts are not successful, the carrier returns the shipment to the certified, central pharmacy, per its arrangement with the pharmacy. The returned product is inspected for evidence of damage or tampering, and it is noted in the exclusive database whether the product is acceptable for reshipment (only applicable if the product has not been delivered and has remained in the carrier's possession and reshipment is only to the same patient). In the event a shipment is lost by the carrier, a replacement shipment cannot be sent until approved by a pharmacist-in-charge at the certified, central pharmacy.

The certified, central pharmacy ensures that only one sensitive drug prescription is being dispensed at any one time to any one patient. Because the certified, central pharmacy contacts the prescriber to renew a prescription before the previous prescription has expired (to ensure continuity of treatment for the patient), new prescriptions often arrive before the current prescription has expired. When a new prescription arrives for a patient who already has an active prescription, the new prescription is put on hold until the prescription already in the exclusive database is depleted. If the certified, central pharmacy receives a prescription for a patient from more than one prescriber, certified, central pharmacy staff will know that the patient already has an active prescription in the exclusive database and will query the patient as to the reason for having more than one prescriber write prescriptions for the patient. If the patient has more than one prescription from more than one prescriber, the certified, central pharmacy will contact each prescriber for clarification. Depending on the clarification received from the different prescribers, the certified, central pharmacy will either terminate the current prescription prior to activating the new one or will put the new prescription on hold until the current prescription has been depleted. If there is a reasonable suspicion that a patient may be doctor shopping for purposes of abuse, misuse, and/or diversion, the prescription will not be filled, the prescriber(s) will be alerted, and the pharmacist at the certified, central pharmacy will complete an RIVER.

Upon receipt of the initial prescription for every patient, the certified, central pharmacy verifies the patient's enrollment and checks the patient's profile in the exclusive database to ensure the patient has not previously enrolled. For each initial prescription, at the time of data entry, the certified, central pharmacy searches the database by last name, city and state, social security number (if provided), and date of birth to verify patient enrollment status. If there are no matches, the pharmacy will proceed with processing this patient as a new enrollment. In some instances, a patient may be enrolled under more than one name (for example, if the patient's name changes because of marriage). When a duplicate patient profile is detected, the certified, central pharmacy ensures that only one profile is active and eligible to receive shipments.

The certified, central pharmacy does not allow shipment to patients who have not enrolled in or have been removed from the REMS program or have stopped treatment using the sensitive drug. Upon receipt of each initial prescription, the certified, central pharmacy checks the enrollment status of each patient and prescriber. At each refill, the certified, central pharmacy contacts the patient to update the patient profile in the exclusive database, which provides another check on enrollment status.

As noted above, a tool used at the certified, central pharmacy to monitor for inappropriate prescribing, misuse, abuse, and/or diversion of the sensitive drug is a risk management report (RMR) Investigations into potential abuse, misuse, and/or diversion can be made a requirement of the REMS program, and the RMR procedures can be a requirement included in the certified, central pharmacy's elements to assure safe use (ETASU) of the REMS program. A pharmacist at the certified, central pharmacy must complete an RMR for any event that gives rise to a reasonable suspicion of abuse, misuse, and/or diversion of the sensitive drug. This includes all requests for an early refill, reports of potential misuse, abuse, and/or diversion, and all reports of lost, stolen, destroyed, or spilled drug.

A completed RMR includes patient identifier and profile information, the date of the event, a descriptive narrative of the event, a record of the certified, central pharmacy contact(s) with the prescriber related to the event, the outcome(s) of the event including any action taken by the certified, central pharmacy related to the event, and a list of any documents or reports related to the event (e.g., adverse event reports, police reports, DEA reports for lost shipments, and/or fire reports). In many cases, RMRs will document investigations that include multiple pharmacy-patient, pharmacy-caregiver, and/or pharmacy-prescriber interactions that transpire over several days. The completed RMR provides a concise compilation of relevant information associated with a potential risk event, and when documented in the exclusive database, provides longitudinal data that the certified, central pharmacy can consult to determine whether a patient's pattern of behavior indicates a likelihood of abuse, misuse, and/or diversion.

The RMR history for each enrolled patient who is receiving a sensitive drug from the certified, central pharmacy is available for consultation and review at the pharmacy, and this review is required as part of a pharmacist's handling of an early refill request or any time the pharmacist suspects abuse, misuse, and/or diversion of the sensitive drug. In addition, the REMS program requires that the pharmacist at the certified, central pharmacy notifies a prescriber in the event of suspected abuse, misuse, and/or diversion of the drug and when a patient has requested an early refill. Any information contained in a patient's RAM history provides an organized summary of previous patient experiences and problems with the drug that can be reviewed with the prescriber to ensure awareness of individual patient behaviors and the possible need for additional patient counseling or other actions, ranging from restrictions on early refills to removal from the REMS program.

Alerts on a patient's and/or caregiver's profile stored in the exclusive database help to direct any subsequent interaction with the patient and/or alert all pharmacy staff of the certified, central pharmacy that this patient or caregiver has a history of potential abuse, misuse, and/or diversion of the sensitive drug and that requests for early refills or reports of lost or stolen drug or other irregularities should be met with greater scrutiny. In the event that a patient changes his or her prescriber, the certified, central pharmacy provides longitudinal information about the patient, including any relevant alerts, to the new prescriber. In addition, pharmacists at the certified, central pharmacy review prior alerts as part of the RMR procedure, ensuring that both the prescriber and pharmacist are aware of a patient's and/or caregiver's history of possible abuse, misuse, and/or diversion.

An early refill request occurs when a patient, caregiver, and/or prescriber report that the patient will not have sufficient quantities of the sensitive drug to last until the next scheduled shipment, and therefore will require drug to be shipped sooner than scheduled. Early refill requests do not include changes to scheduling that are a result of shipment logistics, such as the carrier not shipping on weekends and holidays. In these cases, the product is delivered prior to a patient's next shipment date, but the patient's subsequent refill date does not shift to ensure the patient does not receive more than is prescribed.

The pharmacist at the certified, central pharmacy is required to complete an RMR for every early refill request, notify the prescriber of the request, and monitor a patient's and/or caregiver's history of early refill requests as part of the required monitoring of patients and/or caregivers for abuse, misuse, and/or diversion of the sensitive drug.

Under the REMS program, prescribers are notified regarding concomitant use of contraindicated medications and serious changes in the patient's medical condition. Notifications are documented in the certified, central pharmacy exclusive database. As noted, the REMS program also documents the number of notifications to prescribers for suspected abuse, misuse, and/or diversion, for alerts regarding potential abuse, misuse, and/or diversion on the patient's profile; for early refill requests; and for prescription errors in a way that is accessible for reporting.

Pharmacists at the certified, central pharmacy are required to notify the prescriber of every early refill request. As early refill requests, including repeated requests, may be a sign of abuse, misuse, and/or diversion, pharmacists are required to review the patient's and/or caregiver's RMR history and any alerts, and ensure that the request has been discussed with the prescriber prior to approving the early refill.

To ensure that the informational objectives of the REMS program are achieved, the REMS program requires all prescribers and the certified, central pharmacy to become specially certified in the REMS program, and further requires all patients and caregivers to enroll in the REMS program. Briefly, prescriber certification requires each prescriber to attest that that he or she has read the prescribing information and a REMS program prescriber brochure, and pharmacy certification requires that the pharmacy must, among other things, ensure that all pharmacists complete a REMS program certified pharmacy training program. The pharmacy training program ensures that all pharmacy staff are trained on the risks, safe use, handling, and storage of the sensitive drug and on the requirements of the REMS program, including completing knowledge assessments. The review of these educational and training materials ensures that all prescribers and pharmacists are informed of the risks and safe use of the sensitive drug. Patient and caregiver enrollment (or an association of the caregiver with the patient) requires that patients and caregivers be informed, during the enrollment process by their prescriber, of the risks of the sensitive drug. This informing can be by way of the information contained in a REMS program patient quick start guide, a medication guide, a caregiver brochure that is specific to pediatric patients (or elderly or other special needs patients), and through completion of a REMS program counseling checklist.

Regarding the counseling checklist, prior to dispensing the sensitive drug, a pharmacist at the certified, central pharmacy contacts the patient and completes the REMS program patient counseling checklist, and ensures that the information received is maintained in the REMS program exclusive database of the certified, central pharmacy. The REMS program patient counseling checklist is the primary tool used by the certified, central pharmacy to counsel newly enrolled patients before their first shipment of the sensitive drug and patients restarting use of the sensitive drug after not receiving the sensitive drug for six months or more. The pharmacist will counsel the patient on the checklist.

In addition to the checklist, the exclusive database includes and maintains patient and prescriber enrollment status, all completed REMS forms, prescription and shipment data, as well as information related to dosing, concomitant medications, and behavior that raises suspicion of misuse, abuse, and/or diversion, including complete RMR histories and alerts regarding potential abuse, misuse, and/or diversion on the patient profiles. The exclusive database also contains database-enabled controls and checks to ensure compliance with the REMS program.

More specifically, the information contained in the exclusive database includes the following:

-   -   Prescription date, titration and dosing, and prescriber         instructions. Prescriber information, including all current         patients who are prescribed the sensitive drug and whether the         prescriber's DEA and state license numbers are active.     -   Patient information, including name and two identifiers, current         and previous prescribers, comorbid conditions, concomitant         medications and other potentially interacting agents,         prescription history, and early refill requests and outcomes.     -   Certified, central pharmacy interactions with prescribers,         patients, caregivers, and other parties regarding the patient,         caregiver, prescriber, or prescription, including information         that might suggest potential patient, caregiver, and/or         prescriber misuse, abuse, and/or diversion.     -   Data and information on all shipments of the sensitive drug,         including number and quantity of shipments sent daily.

Prior to dispensing a newly enrolled patient's first-time fill, a pharmacist at the certified, central pharmacy completes the patient counseling checklist, asking each patient for a list of his or her current medications and doses. The certified, central pharmacy also asks a patient if his or her medications have changed at the time of the scheduling call for subsequent shipments, and a pharmacist must notify, the prescriber when the patient is receiving concomitant contraindicated medications.

Upon implementation of the REMS program, patient-reported changes in concomitant medications during any refills and notifications to prescribers are captured through the completion of the REMS program patient counseling checklist. Capture of these medications, with the subsequent confirmation regarding prescriber notification in the checklist, enables accurate reporting of data from both first fills and refills for assessment purposes.

An example embodiment of a restricted distribution program for a sensitive drug is illustrated in FIG. 2, and as noted above, can be referred to as a Risk Evaluation and Mitigation Strategy (REMS). The REMS system 200 begins with prescriber and patient enrollment, screening, counseling, and educating. Specifically, as illustrated at 205, a prescriber is enrolled in the REMS program. The prescriber enrollment 205 includes providing prescribing information and a prescribing program brochure to the potential prescriber. After review of the information and brochure, the prescriber can fill out a prescriber enrollment form. This prescriber enrollment form is submitted to a certified, central pharmacy, as will be discussed in more detail in connection with operation 215.

In a similar fashion, as indicated at 210, potential patients, including pediatric patients and caregivers associated with those pediatric patients, are screened, selected, counseled, and enrolled. It is noted that an elderly patient or other special needs patient, like a pediatric patient, can also have a caregiver, although it is not a strict requirement like in the case of a pediatric patient. The screening, selecting, counseling, and enrolling procedures include providing to the patient and caregiver a patient quick start guide, a medication guide, and a patient enrollment form. Additionally, a brochure is provided to the caregiver that is specific to pediatric patients (or elderly or other special needs patients). The patient quick start guide, medication guide, and brochure instruct and educate the patient and caregiver on the proper use, dosing, and handling of the sensitive drug. After review of the patient quick start guide, the medication guide, and the brochure, the patient and/or caregiver can till out a patient enrollment form. This patient enrollment form is submitted to a certified, central pharmacy, as will be discussed in more detail in connection with operation 215.

As indicated at 215, a certified, central pharmacy includes an enrollment team. The enrollment team verifies the completion of the prescriber and patient enrollment forms, and enters the prescriber, patient, and if present caregiver, information into the exclusive database of the certified, central pharmacy. At 215A, the certified, central pharmacy notifies the prescriber or patient (and if appropriate the caregiver), as the case may be, of the successful enrollment, and as indicated at 215B, a welcome message is transmitted to the patient and/or caregiver such as via a telephone call, an email message, a mailed letter, a text message, or any other form of suitable communication.

After successful enrollment of a prescriber, the enrolled prescriber can prescribe the sensitive drug to one or more enrolled patients. Similarly, after successful enrollment of a patient, the enrolled patient can be prescribed the sensitive drug by an enrolled prescriber. The writing of a prescription for the sensitive drug is done using a REMS program prescription form (220). At 222, the prescriber transmits the prescription form to the certified, central pharmacy. Upon receipt of the prescription form, the certified, central pharmacy verifies the prescriber, patient, and caregiver information on the prescription form with the prescriber, patient, and caregiver information in the certified, central pharmacy's exclusive computer database. As noted previously, the prescriber, patient, and caregiver information in the certified, central pharmacy's exclusive database was extracted from the prescriber and patient enrollment forms.

Operation 230 commences the duties of the certified, central pharmacy's services team. Specifically, at 230, the certified, central pharmacy's services team validates the non-prescriber and non-patient prescription information (that is, the actual prescription information) on the prescription form. After the prescription information is validated, the prescription information is entered into the certified, central pharmacy's exclusive database. As noted elsewhere in this specification, requiring the entry into the certified, central pharmacy's exclusive database of all prescribers prescribing the prescription drug and all patients being prescribed the prescription drug assists in preventing abuse, misuse, and/or diversion of the prescription drug. At 232, the certified, central pharmacy notifies the prescriber that the certified, central pharmacy has received the prescription request from the prescriber.

At 234, the certified, central pharmacy verifies that the patient and any associated caregiver have completed the required counseling, and/or provides additional counseling and responds to any questions or concerns of the patient and/or caregiver. To ease the verification process for the certified, central pharmacy, the certified, central pharmacy can employ a counseling checklist, which can include items such as verifying that the patient or caregiver has read the educational materials, has completed all necessary forms, has completed any tests and/or assessments, and as explained in more detail herein, the patient has an associated caregiver if the patient is a pediatric patient. That is, the check list ensures that the patient is educated and counseled about safe use and handling of the sensitive drug and about the requirements of the RIMS program, and documents information about concomitant medication use and comorbidities.

At 236, the certified, central pharmacy uses its computer systems and its exclusive database to conduct an electronic drug utilization review. In an embodiment, the electronic drug utilization review queries the exclusive database to determine what, if any, other pharmaceuticals the patient is presently taking or has taken in the past. For any pharmaceuticals that the patient is taking or has taken, the system checks its database to determine if any of these pharmaceuticals may cause an adverse reaction if taken in conjunction with the sensitive drug. If there is a potential for adverse reaction, the system notifies personnel of the certified, central pharmacy, and the personnel can take the appropriate action.

If the electronic drug utilization review does not identify any other pharmaceuticals that could cause an adverse reaction in connection with the sensitive drug, or any potential adverse reactions with other pharmaceuticals have been adequately addressed by certified, central pharmacy personnel, then the certified, central pharmacy proceeds with the dispensing, packaging, and shipment of the sensitive drug at 237. The dispensing involves placing the correct amount of the sensitive drug into the correct number and size of containers. The packaging of the sensitive drug includes adding the sensitive drug containers into a packaging/shipping box or other container, and adding incidentals such as measuring cups or other apparatus, a copy of the medication guide, and a copy of the patient quick start guide, and a copy of the caregiver brochure that is specific to pediatric and other special needs patients. The entire package is then shipped to the patient and/or the caregiver associated with the patient. In an embodiment, this shipment is via an overnight carrier.

At 238, the prescriber is notified of the shipment of the sensitive drug to the patient. Such notification can occur for only the first shipment of the sensitive drug, or for any shipment of the sensitive drug to the patient. Such notification enables the prescriber to follow the prescription history of the sensitive drug to the patient, and to more easily become aware of any abuse, misuse, and/or diversion of the sensitive drug.

Beginning at 240, operations are described that relate to the reception of the sensitive drug by the patient and/or caregiver, and the administering of the sensitive drug to the patient. Specifically; at 240, the patient and/or caregiver receives the sensitive drug via the delivery service, and signs for the sensitive drug before the delivery service leaves the sensitive drug with the patient and/or the caregiver. Two items are noteworthy here. The sensitive drug is only available through the certified, central pharmacy and its associated exclusive database; it is not available for delivery through a retail pharmacy. Also, the certified, central pharmacy can receive an immediate electronic communication from the delivery service that the sensitive drug has been delivered to and signed/accepted by the patient and/or the caregiver. The certified, central pharmacy can then also inform the prescriber that the sensitive drug has been successfully delivered to the patient. These procedures and sub-procedures contribute to the certified, central pharmacy's ability to prevent abuse, misuse, and/or diversion of the sensitive drug.

At 241, the patient and/or caregiver appropriately stores the sensitive drug. The appropriate storage of the sensitive drug is outlined and explained in the medication guide, the patient quick start guide, and the brochure provided to the caregiver that is specific to pediatric and other special needs patients. Storage requirements can involve such matters as the proper environment for the sensitive drug (light, temperature, humidity, etc.) and prevention of access of the drug by other persons (for example, storing the sensitive drug in a locked cabinet).

At 242, the patient and/or caregiver prepares a dosage of the sensitive drug. In a simple situation, this may only involve removing a pill, tablet, or capsule from its container, and taking or administering the sensitive drug to the patient with the proper type and amount of fluids and food. In a more complex situation, there may be multiple doses within a particular time period, wherein that time period may be during nighttime hours, and the sensitive drug may be in a liquid form that requires a measuring of the proper amount of the sensitive drug.

More specifically, as illustrated at operations 243 and 244, there is an administering of the sensitive drug in a first dosage and a second dosage. For example, as could be explained in the medication guide, the patient quick start guide, or the caregiver brochure, no food should be consumed during a certain time period prior to administering the sensitive drug. For example, no food should be consumed two hours (or less) before the sensitive drug is taken. If the sensitive drug relates to the treatment of sleep disorders, it may be required that the sensitive drug is only taken in bed, just prior to laying down in bed to sleep for the night. Additionally, if the second dose is to be taken before the patient wakes in the morning, the patient should set an alarm so that the patient can wake up and take the second dose of the sensitive drug. The second dose should be at the patient's bedside, so that the patient can take the second dose in bed, and immediately lay down again and return to sleep for the night. There may be additional provisos such as not operating any vehicles or machinery for a certain time period after any dose. The proper dosage regime of operations 243 and 244 are once again outlined and explained in the medication guide, the patient quick start guide, and/or the caregiver brochure.

At 250, the prescriber follows up with the patient (or associated caregiver) to verify that the patient is taking the sensitive drug in the appropriate manner, and to determine if there are any other issues with the patient and/or caregiver that need to be addressed. In addition to the prescriber follow-up, the certified, central pharmacy may also follow up with the patient and/or caregiver to determine that the sensitive drug is being properly administered and that there are no issues with the patient and/or caregiver.

Another embodiment of a REMS restricted distribution program 300 for a sensitive drug is illustrated in FIG. 3. At 305, a task is pulled from a queue. This task queue represents actions that have to be taken by the certified, central pharmacy in relation to distributing the sensitive drug, from enrollment to shipping to follow-up.

At decision block 310, the computer system of the certified, central pharmacy determines if the task in the queue relates to some type of form. If the task does not relate to a form, the system moves on to an outreach to the patient (and/or associated caregiver) as noted in operation 325, which is discussed in detail below. If the task does relate to a form, then at 315, the certified, central pharmacy determines if the form is a REMS form (that is, an enrollment form). If the task is a REMS form, then the form is formally categorized as a REMS form at 316, and at 317, a case is created for the patient that includes all the information needed to enroll the patient in the REMS system such as name, date of birth, gender, height, weight, etc.

If the certified, central pharmacy determines at operation 315 that the task is not a REMS form, then the certified, central pharmacy categorizes the form as a prescription form at 318. That is, the form at 318 is from a prescriber who is prescribing a sensitive drug to a patient. Then at 319, a case is created for this particular drug for this particular patient for this particular prescription.

At decision block 320, the certified, central pharmacy determines whether the creation of the REMS case at operation 317 has been completed. If the creation of the REMS case has not been completed, the remaining data are entered at operation 321. Such remaining data can include any data relating to the new patient enrollee (and/or associated caregiver) that was not previously available, such as marital status. After entering the remaining data at operation 321, a final review of the completed REMS form is performed at 322.

At operation 325, a patient (and/or caregiver) outreach is performed. This outreach occurs both after the certified, central pharmacy determines at 320 that the REMS form has not been completed, and after the certified, central pharmacy, creates at 319 a prescription form that was written by a particular prescriber for a particular sensitive drug for a particular patient. For the uncompleted REMS form, the patient outreach may be to determine the information that is missing from the REMS form. For the prescription form, the outreach may be able to determine if the patient has begun taking any other prescription drugs, since the patient's enrollment in the REMS program, wherein such other prescription drugs could possibly negatively affect the patient if the patient begins taking the new sensitive drug.

At decision block 326, the certified, central pharmacy determines whether there was a response from the patient to the outreach to the patient at 325. If there was a patient response, then at 327 the REMS form is first corrected and/or updated, and at 328, the patient's case is set to pending. That is, it is waiting for a prescription to be received at the certified, central pharmacy or it is waiting for the certified, central pharmacy to act on distributing a pending prescription. If a response was not received from the patient at 326, then at 329, the certified, central pharmacy dockets a note to follow up with a call to the patient.

The central database described above is a relational database running on the system of FIG. 1, or a server-based system having a similar architecture coupled to workstations via a network, as represented by communications 160. The database is likely stored in storage 140, and contains multiple fields of information as indicated at 400 in FIG. 4. The organization and groupings of the fields are shown in one format for convenience. It is recognized that many different organizations or schemas may be utilized. In one embodiment, the groups of fields comprise prescriber fields 410, patient fields 420, prescription fields 430, caregiver fields 435, and insurance fields 440. For purposes of illustration, all the entries described with respect to the above processes are included in the fields. In further embodiments, no such groupings are made, and the data are organized in a different manner.

Several queries are illustrated at 500 in FIG. 5. There may be many other queries as required by individual state reporting requirements. A first query at 510 is used to identify prescriptions written by physician. The queries may be written in structured query language, natural query languages or in any other manner compatible with the database. A second query 520 is used to pull information from the database related to prescriptions by patient name. A third query 530 is used to determine prescriptions by frequency. A fourth query 535 is used to determine prescriptions by caregiver, and an n^(th) query finds prescriptions by dose at 540. Using query languages combined with the depth of data in the central database allows many other methods of investigating for potential abuse of the drugs. The central database ensures that all prescriptions, prescribers, patients, and caregivers are tracked and subject to such investigations. In further embodiments, the central database may be distributed among multiple computers provided a query operates over all data relating to such prescriptions, prescribers, patients, and caregivers for the drug.

An example of one prescription and enrollment form is shown at 600 in FIG. 6. As previously indicated, several fields are included for prescriber information, prescription information, patient information, and caregiver information.

FIG. 7 is a copy of one example NORD application request form 700 used to request that an application be sent to a patient and/or caregiver for financial assistance.

FIG. 8 is a copy of one example application 800 for financial assistance as requested by form 800. The form requires patient, caregiver, and physician information. Social security number information is also requested. The form provides information for approving the financial assistance and for tracking assistance provided.

FIG. 9 is a copy of one example voucher request for medication for use with the NORD application request form of FIG. 7. In addition to patient, caregiver, and physician information, prescription information and diagnosis information is also provided.

FIGS. 10A, 10B and 10C are descriptions of sample reports obtained by, querying a central database having fields represented in FIG. 4. The activities grouped by sales, regulatory, quality assurance, call center, pharmacy, inventory, reimbursement, patient care and drug information. Each report has an associated frequency or frequencies. The reports are obtained by running queries against the database, with the queries written in one of many query languages.

While an embodiment of the invention has been described with respect to a Schedule III drug, it is useful for other sensitive drugs that are DEA or Federally scheduled drugs in Schedule as well as still other sensitive drugs where multiple controls are desired for distribution and use.

Another embodiment is directed to a controlled distribution of a prescription drug to a pediatric patient base (or elderly or other special needs patient base), and in particular a prescription drug that is susceptible to abuse, misuse, and/or diversion. Similar to previously-described embodiments, these other embodiments utilize one or more of a central pharmacy and an exclusive computer database. Additionally, similar to previously-disclosed embodiments, these other embodiments maintain data on prescriptions, prescribers, and patients, and track these data to identify potential abuse, misuse, and/or diversion. As noted above, these previously-disclosed embodiments have become to be referred to as Risk Evaluation and Mitigation Strategies (REMS). The new other embodiments add several features, including associating a pediatric, elderly, or other special needs patient with a responsible caregiver, maintaining data on caregivers, and analyzing the data to identify potential abuse, misuse, and/or diversion of the prescription drug by the pediatric patients and/or caregivers. An eBook is also part of these additional REMS system embodiments, which makes it easier for patients and caregivers to review the educational material on the prescription drug, allows for automatic verification that the patient and/or caregiver have reviewed the material, and permits testing of the patient and/or caregiver to verify that the patient and/or caregiver have reviewed and understand the material. In yet another embodiment, the eBook can include a survey that is administered to the patient and/or caregiver. This survey can be used to determine, among other things, the effectiveness of the eBook and the contents thereof.

FIGS. 11A, 11B, 11C, 11D, 12A, and 12B are block diagrams illustrating features and operations of a system and method of distributing a prescription drug under exclusive control of an exclusive central pharmacy, and in particular, distributing a prescription drug to a pediatric patient (or elderly or other special needs patient) who is associated with a caregiver, and monitoring the patient, the prescriber, and the caregiver to identify potential abuse, misuse, and/or diversion of the prescription drug. FIGS. 11A, 11B, 11C, 11D, 12A, and 12B include a number of process blocks 1102-1181 and 1210-1243. Though arranged somewhat serially in the examples of FIGS. 11A, 11B, 11C, 11D, 12A, and 12B, other examples may reorder the blocks, omit one or more blocks, and/or execute two or more blocks in parallel using multiple processors or a single processor organized as two or more virtual machines or sub-processors. Moreover, still other examples can implement the blocks as one or more specific interconnected hardware or integrated circuit modules with related control and data signals communicated between and through the modules. Thus, any process flow is applicable to software, firmware, hardware, and hybrid implementations.

Referring now specifically to FIGS. 11A, 11B, 11C, and 11D, at 1110, prescription requests are received into a computer processor. The prescription requests are received from any and all medical doctors allowed to prescribe the prescription drug. The prescription requests are received for any and all patients that are being prescribed the prescription drug. All of these prescription requests are received only at an exclusive central pharmacy (also referred to as a certified, central pharmacy). In an embodiment, an exclusive central pharmacy is a pharmacy that is the only pharmacy that is permitted to process prescriptions for the prescription drug. By requiring that all of the prescription requests are received only at the exclusive central pharmacy, the system and method establish a high degree of control over the distribution of the prescription drug, and the system and method can more easily identify potential abuse, misuse, and/or diversion of the prescription drug, which will be explained in more detail in the following paragraphs. The prescription requests contain information that identify not only the patients, the prescribers, and the prescription drug, but also a caregiver who is associated with the patient, and in particular, a pediatric patient. Credentials of the any and all medical doctors are also entered into the computer processor.

As disclosed in operation 1120, the system and method require that the information is entered into an exclusive computer database that is associated with the exclusive central pharmacy. The exclusive central pharmacy can then use the exclusive computer database to analyze the prescription, patient, caregiver, and medical doctor data to identify potential abuse, misuse, and/or diversion situations. The requirement that all prescriptions for the prescription drug are processed only by the exclusive central pharmacy using only the exclusive computer database makes the system's ability to identify potential abuse, misuse, and/or diversions more robust by accessing the protected data in the exclusive computer database that has been collected over a period of time and using that data for proactively monitoring patient safety.

At 1130, the computer processor checks the credentials of the any and all medical doctors to determine the eligibility of the medical doctors to prescribe the prescription drug. At 1140, the method provides for confirming with a patient and a caregiver associated with the patient that educational material has been read prior to shipping the prescription drug. It can be important that both the patient and caregiver have read the educational material (notwithstanding that, as disclosed below, the caregiver may not be viewed as a stakeholder), since both are intimately involved with the treatment of the patient, and both must therefore understand the proper handling of the prescription drug.

At 1150, the computer processor checks/queries the exclusive computer database for potential abuse, misuse, and/or diversion of the prescription drug. For example, the computer processor can check to see if a patient or caregiver is requesting too many early refills, and/or if a medical doctor is prescribing an inordinate number of prescriptions to an inordinate number of patients. At 1150A, information and data are entered into and maintained in the exclusive computer database that indicate that a patient, a caregiver, and/or a prescriber has abused, misused, and/or diverted the prescription drug. This information can be gleaned from checking the database via queries, as just discussed in connection with operation 1150. Alternatively, this information can be directly entered by an official of the central pharmacy after identifying a potential abuse, misuse, and/or diversion of the prescription drug via some means other than a database query. At 1160, the prescription drug is mailed or otherwise delivered to the patient only if no potential abuse, misuse, and/or diversion is found by the patient to whom the prescription drug is prescribed, the caregiver associated with the patient, and the medical doctor prescribing the prescription drug. As noted throughout this specification, potential abuse, misuse, and/or diversion by the patient could be identified by a patient requesting early refills or claiming that prescriptions have been stolen, lost, or spilled. Potential abuse, misuse, and/or diversion by the caregiver could be identified in a similar manner. Potential abuse, misuse, and/or diversion by the medical doctor could be identified, for example, if the medical doctor writes prescriptions for early refills for several patients.

In another embodiment, as outlined at 1162, the system and method check for abuse, misuse, and/or diversion with the exclusive computer database by transforming prescription data, patient data, caregiver data, and prescriber data into one or more queries to access data in the exclusive computer database that relates to abuse, misuse, and/or diversion. The results of the queries can indicate whether abuse, misuse, and/or diversion has potentially occurred and should be investigated. In another embodiment, as indicated at 1163, the system and method control the distribution of the prescription drug based upon the transformation of the prescription data, patient data, caregiver data, and prescriber data in response to the checking for abuse, misuse, and/or diversion, and authorize filling of a prescription for the prescription drug if there is no record of an incident that indicates abuse, misuse, and/or diversion by the patient, the caregiver, and/or the prescriber. If there is a record of such incident, the exclusive computer database indicates that such incident has been investigated, and the exclusive computer database indicates that such incident does not involve abuse, misuse, and/or diversion.

At 1170, the system and method confirm receipt of the prescription drug by, the patient or the caregiver associated with the patient. Such confirmation can be accomplished by having the patient and/or caregiver electronically sign using a mobile device of the delivery service, and receiving at the computer processor of the exclusive central pharmacy confirmation directly from the mobile device of the delivery service (or an intermediate server of the delivery service or other party).

At 1180, the system and method generate with the computer processor and the exclusive computer database periodic reports on a regular time basis to evaluate potential diversion patterns. A regular time basis has equally spaced time intervals between reports, and such reports are not generated in response to a specific report or incident of abuse, misuse, and/or diversion. A potential diversion pattern could be identifying that a caregiver has claimed that there have been three spillage incidents of the prescription drug within the last three months. Those of skill in the art will realize that other patterns could be identified. At 1181, the system and method selectively block shipment of the prescription drug to the patient or the caregiver based on a determination of potential abuse, misuse, and/or diversion by the patient or the caregiver.

At 1141, it is noted that the educational material can be an electronic file. When the educational material is an electronic file, the process of confirming that the patient and the caregiver have read the educational material can include receiving, in response to viewing the electronic file by the patient and the caregiver, input from the patient and the caregiver (1141A). This input can be, in an embodiment, a simple clicking on a button indicating that the patient and/or caregiver have read/reviewed the educational material. At 1141B, the system and method transmit, to the exclusive computer database, the received input from the patient and/or the caregiver relating to the viewing of the educational material. As indicated at 1142, the system and method confirm with the caregiver that the caregiver has educated each and every adult who is assigned caregiver responsibilities. Ensuring that all persons with caregiver responsibilities are properly educated further decreases the likelihood that the prescription drug with be abused, misused, and/or diverted.

In another embodiment wherein the educational material is an electronic file, the system and method at 1143A automatically confirm that the patient and/or the caregiver has opened the electronic file. This embodiment does not rely on the veracity of the input of the patient and/or caregiver, thereby mitigating another possible source of abuse, misuse, and/or diversion. In another embodiment, as indicated at 1143B, the system and method programmatically ensure that the patient and/or caregiver reviews the material from the beginning to the end in sequential order. After a complete review of the file, the system and method permit free movement through the file. Thereafter, at 1143C, the system and method transmit to the exclusive computer database the confirmation that the patient and/or the caregiver have opened the electronic file. In yet another embodiment, the system and method can determine whether the patient or caregiver has clicked on a link in the electronic file. The system and method can further programmatically keep track of and determine the amount of time that a patient or caregiver spends on viewing certain pages and/or sections in the electronic file (1143D).

As noted at 1144, the electronic file can be an eBook. The eBook can include links for navigating through the eBook, a test section for testing whether the patient and/or the caregiver have read and understand material in the eBook, and logic for determining that a score on the test section by the patient and/or the caregiver exceeds a threshold (1144A). This embodiment is an advance on a simple confirmation that the patient and/or caregiver have simply opened the electronic file or eBook. Specifically, the eBook will have to be read by the patient and/or caregiver in order to achieve a sufficient score on the test. At 1144B, the system and method transmit the confirmation to the exclusive computer database only when the patient and/or the caregiver achieves a sufficient score, that is, the score exceeds a threshold.

Further aspects and features of the eBook are as follows. The eBook can include different content for different ages of pediatric patients. That is, the content would likely be different if directed to a seven year old patient versus a seventeen year old patient (1144D). In a related embodiment, the eBook is operable to receive input from the caregiver, such that the caregiver can select the particular age-appropriate version of the eBook suitable to the pediatric patient associated with the caregiver (1144E).

Additionally, as noted at 1144G, the eBook is capable of calculating a titration or dosage for the patient. The patient and/or caregiver would provide certain information such as age of the patient, gender of the patient, and weight of the patient, and the eBook processor will calculate the appropriate dosage and/or titration. The calculated dosage and/or titration can then be displayed on the display unit of the eBook.

The eBook is also operable to remind the patient and/or caregiver of an upcoming refill. After the reminder is conveyed to the patient and/or caregiver, the eBook can receive input from the patient and/or caregiver indicating a desire for the refill, and the eBook can transmit the refill request to the exclusive central pharmacy (1144I).

As indicated at 1144K, the eBook is operable to receive input from the patient or the caregiver associated with the patient to register in a distribution program associated with the exclusive central pharmacy to receive the prescription drug and to transmit the input to a medical doctor for registering the patient with the exclusive central pharmacy. The eBook can then also receive input from the patient or caregiver to receive the initial prescription request from the patient or caregiver. Further, the eBook can receive input from the patient or caregiver to modify the patient information or caregiver information. The patient or caregiver can also receive via the eBook a message from the prescriber and/or the exclusive central pharmacy. In an embodiment, the eBook can include security features such as fingerprint recognition, retinal recognition, face recognition, and/or voice recognition to control access to the contents of the eBook.

The eBook can be entirely electronic in nature, or it can be a physical publication that includes an electronic component. For example, as illustrated in FIG. 13, a physical material brochure or book 1310 includes an electronic display 1320 that is coupled to a computer processor (not pictured in FIG. 13) that is embedded in or attached to the eBook in some manner. Any input received from the user via a hard button, a soft button, or other input from a touch sensitive electronic display on the eBook can be wirelessly transmitted to the central pharmacy. In an embodiment, the eBook contains an educational display region 1321, a testing display region 1322, an educational display region for pediatric-patient level educational information 1323, and a testing display region for a pediatric-patient test section 1324.

As indicated at 1111, the system and method can accommodate a situation wherein two or more caregivers are associated with a patient and/or two or more patients. Such an association can include virtually any familial relationship, such as two parents and three children; a parent, a grandparent, and a child; and a parent, an older sibling of the patients, and two child-patients, just to provide a few examples. The system and method also permit the two or more caregivers to be associated with two or more residences (1111A). This two-residence feature permits the system and method to more easily identify abuse, misuse, and/or diversion when the caregiver parents of the pediatric patient are separated or divorced. In any such situation, the system and method check the exclusive computer database for potential abuse of the prescription drug by one or more of the two or more caregivers (1111B). In an embodiment, the exclusive computer database is structured such that if only one of the caregivers is suspected of being the source of an abuse, misuse, and/or diversion of the prescription drug, at least because of the system's ability to maintain separate residences of the two caregivers, the system can identify the particular caregiver who is suspected of the abuse, misuse, and/or diversion. Likewise, at 1111C, the system and method can determine that the patient and the caregiver are residents of a same household, and the system and method can associate any potential abuse, misuse, and/or diversion of the prescription drug with that same household. More specifically, the system can track usage wherein there are multiple patients and/or caregivers who are patients in the same household. For example, if a mother is a caregiver and/or a patient, and two of the mother's children are also patients, then the system can monitor all of the mother and the two children as part of the same household. This functionality of the system addresses a scenario wherein the mother requests early refill for herself and for her two dependent children. Even though the mother and two children will all have separate patient identifiers, the system can interrelate the prescription requests of the mother and two children because the system knows that all three are within the same household. This triangular or higher order ability further permits the system to identify abuse, misuse, and/or diversion of the prescription drug. In another embodiment, as indicated at 1111E, the system and method associate the caregiver with two or more patients. In such an embodiment, the system and method check the exclusive computer database for potential abuse of the prescription drug by the caregiver or the two or more patients in much the same manner as when there are multiple patients associated with a caregiver as just described.

The system and method can also handle the situation wherein the caregiver is also a patient for whom the prescription drug is prescribed (1112). This can be accomplished by storing the caregiver's name in both the patient and caregiver's fields in the exclusive computer database, setting a flag associated with the caregiver field, and/or some other data structure technique known to those of skill in the art. Additionally, both patients and caregivers are associated with a unique identification (ID) in the system, and the patient and caregiver can be linked via these Ds. These IDs can further be used to monitor the patients and caregivers over an extended period of time, which contributes to the effectiveness of identifying abuse, misuse, and/or diversion. Whatever the implementation of the situation wherein the caregiver is also a patient, the system and method check the exclusive computer database for abuse of the prescription drug by either the patient or the caregiver-patient (1112A). The exclusive computer database can be further structured to permit the determination of whether a person is acting as a patient or a caregiver. For example, when the person signs for receipt of the prescription drug for the pediatric patient (or elderly or other special needs patient), it can be noted that the person for this transaction is acting as the caregiver. Thereafter, if the caregiver requests an early refill for the patient (and not for the caregiver as a caregiver-patient), then it can be determined that the person could be the source of an abuse, misuse, and/or diversion of the prescription drug as the caregiver.

The system and method can further determine that a particular patient is not associated with any caregiver, or that the particular patient is no longer associated with any caregiver (1113). Such a determination can be accomplished by checking that the caregiver field associated with a particular patient has data in it, and that the data are verified to the extent possible. For example, the system and method can check other sources to verify the data associated with the caregiver, such as the age of the caregiver. In an embodiment, the system and method can periodically check with the caregiver, for example via an email or text message that the caregiver is still serving in a caregiving capacity for the associated patient. At 1113A, if there is an indication that no caregiver is associated with a patient, or that a caregiver previously associated with the patient is no longer acting as a caregiver, the system and method prevent shipment of the prescription drug to the particular patient. Sometime thereafter, the system and method can access the exclusive database again to determine if the pediatric patient has transitioned to a new caregiver (1113B), so that shipments can be re-started (1113C). In another embodiment, as indicated at 1113E, the system and method can probe the caregiver upon a refill request, counseling with the caregiver, or other contact with the caregiver. This probing can be used to verify that the caregiver is still acting as the caregiver for the patient; and when the caregiver is no longer acting as the caregiver for the patient, selecting a new caregiver for the patient before the refill is filled. In an embodiment, the selection of a new caregiver for a patient involves acquiring information about the new caregiver, inputting the information into the system, and then associating the patient with the new caregiver.

In another embodiment, as indicated at 1113G, the system and method determine that a pediatric patient is no longer associated with a caregiver because the pediatric patient has attained a certain age (e.g., 18 years of age), and that patient is then no longer considered a pediatric patient, but rather an adult patient. Such a new adult patient may not need a caregiver. The transition from a pediatric patient with a caregiver to an adult patient with no caregiver can be facilitated by both the eBook and patient activity (e.g., submission of a form) at the pharmacy. This allows for the system to proceed without requiring the (former) caregiver to go into the prescriber's office. The transition from a pediatric patient to an adult patient can be driven by the patient, the caregiver, and/or the prescriber, at least after the patient turns 18 years of age. So once the patient turns 18 year of age, one of the patient, caregiver, and/or prescriber can request the initiation of this transition process, and the system can ensure that the appropriate attestation is obtained from the patient that they are assuming responsibility for their own care, and they will be treated as an adult from that point on. In another embodiment, an emancipated minor (less than 18 years of age) would follow an analogous process, except that they would not have to be 18 years of age or older.

In another embodiment, as indicated at 1113I, the system and method determine, by checking the exclusive computer database, that the patient is no longer associated with a caregiver. In this instance, as contrasted with 1113A wherein shipment is blocked because the patient still requires a caregiver, the system and method determine that the patient has attained an age wherein the patient no longer needs to be associated with the caregiver, for example, the age of 18 years or older.

As noted at 1114, the prescription drug can include multiple formulations from a brand manufacturer and a generic manufacturer. In such a situation, the system and method can determine that the potential abuse is associated with the formulation from the brand manufacturer or the formulation from the generic manufacturer. The ability to make this distinction can assist in identifying whether a particular formulation is susceptible to abuse, misuse, and/or diversion. The ability to make this determination and/or distinction is made possible by the system and method requiring that all the prescription requests for the formulations of the brand manufacturer and the formulations of all generic manufacturers are stored in the exclusive computer database associated with the central pharmacy (1114A).

FIGS. 12A and 12B are a block diagram illustrating another embodiment of a system and method for distribution of a prescription drug that has a potential for abuse, misuse, and/or diversion, and in particular, distribution of the prescription drug to a pediatric patient (or elderly or other special needs patient) population. The embodiments of FIGS. 12A and 12B include one or more computer memories for storing a single computer database having a database schema that contains and interrelates prescription fields, patient fields, caregiver fields, and prescriber fields (1210). The prescription fields 1212 are contained within the database schema, and the prescription fields 1212 store prescriptions for the prescription drug with the potential for abuse, misuse and/or diversion. The patient fields 1214 are contained within the database schema, and the patient fields 1214 store information sufficient to identify the patient for whom the prescription drug is prescribed. The caregiver fields 1216 are contained within the database schema, and the caregiver fields 1216 store information sufficient to identify a caregiver who is associated with the patient. The prescriber fields 1218 are contained within the database schema, and the prescriber fields 1218 store information sufficient to identify a physician or other prescriber of the prescription drug and information to show that the physician or other prescriber is authorized to prescribe the prescription drug.

The embodiments of FIGS. 12A and 12B, at 1220, processes a database query that operates over all data related to the prescription fields, prescriber fields, patient fields, and caregiver fields, and at 1230, the system and method reconcile inventory of the prescription drug before the shipments for a day or other time period are sent by using the database query to identify information in the prescription fields, prescriber fields, patient fields, and caregiver fields. The database query and the reconciling inventory identify potential abuse, misuse, and/or diversion by the patient and/or the caregiver (1240). The system and method then, based on that identification of the potential abuse, misuse, and/or diversion, notify the physician, who is interrelated with the patient through the schema of the single computer database, about the potential abuse, misuse, and/or diversion. The physician can then take action to address the potential abuse, misuse, and/or diversion by contacting the patient and/or caregiver, or take other action to investigate the identified potential abuse, misuse, and/or diversion. In an embodiment, the inventory reconciliation is performed where current inventory is counted and reconciled with database quantities before shipments for a day or other time period are sent, and the system and method selectively block shipment of the prescription drug based on the inventory reconciliation.

In another embodiment, one or more database queries check for abuse, misuse, and/or diversion within the central computer database. Thereafter, a prescription is authorized for the prescription drug only if there is no record of incidents that indicate abuse, misuse, and/or diversion by the patient, caregiver, or prescriber. If there is a record of such incidents, the central computer database indicates that such incidents have been investigated, and the central computer database indicates that such incidents do not involve abuse, misuse, and/or diversion.

At 1221, the system and method process a second database query. The second database query identifies that the patient is a cash payer and identifies a physician that is interrelated with the patient through the schema of the single computer database. As noted at 1221A, the identification that the patient is a cash payer by the second database query is an indicator of potential abuse, misuse, and/or diversion by the patient and/or caregiver and is used to notify the physician that is interrelated with the patient through the schema of the single computer database. Since payment for the prescription drug in cash may be an indication of a patient who does not want to leave a paper trail associated with the purchase of the prescription drug, payment in cash therefore may be indicative of a situation that could lead to abuse, misuse, and/or diversion of the prescription drug.

At 1241, the system and method selectively block shipment of the prescription drug to the patient and/or caregiver based upon the identification of potential abuse, misuse, and/or diversion by the database query. In the alternative, at 1241A, if no abuse, misuse, and/or diversion is found by the patient or caregiver via the database query, the prescription drug is shipped to the patient and/or caregiver.

As indicated at 1211, the single computer database is an exclusive database that receives data associated with all patients being prescribed the prescription drug. And as indicated at 1211A, an exclusive central pharmacy controls the single computer database. As indicated at 1211B, the single computer database can be distributed among multiple computers. In such an embodiment, the database query that checks for potential abuse, misuse, and/or diversion of the prescription drug operates over all data relating to the prescription fields, prescriber fields, patient fields, and caregiver fields.

In an embodiment, the system and method initiate an inquiry to a prescriber when one or more prescription fields, patient fields, caregiver fields, or prescriber fields are incomplete in the computer database (1242). For example, when there is no caregiver associated with a pediatric patient, this can be considered an automatic potential abuse, misuse, and/or diversion situation that needs to not only be investigated but remedied as soon as possible (by identifying a caregiver who will be associated with the pediatric patient).

At 1221B, the system and method process a third database query that identifies an expected date for a refill of the prescription drug. The expected date is based on a prescription for the prescription drug and a date of a previous filling of the prescription. The prescription identifies an amount of the prescription drug to be provided and a schedule for consumption of the prescription drug. The system and method, via the third database query, can predict when a refill should occur, and if an attempt is made to refill the prescription before the anticipated refill date, the attempted refill can be questioned. It is noted that such an early refill attempt may be quite legitimate. For example, a patient may be going on an extended trip, and the prescription needs to be refilled before the trip.

At 1243, the system and method use the single computer database to identify a current pattern or an anticipated pattern of abuse of the prescription drug. The current pattern or the anticipated pattern is identified using periodic reports generated on a regular basis from the single computer database. The term regular basis means that the reports are generated at equally spaced time intervals, and not sporadically such as after a situation of abuse, misuse, and/or diversion has been identified. In this embodiment, one or more controls for distribution of the prescription drug are selected based on the identified pattern, and the one or more controls are submitted to an approval body for approval of distribution of the prescription drug.

At 1244, the current inventory is cycle counted and reconciled with database quantities before shipments for a day or other time period are sent.

At 1211C, the single computer database is an exclusive computer database of a company that obtained approval for distribution of the prescription drug. In this embodiment, all prescriptions for the company's prescription drug are stored only in the exclusive computer database of the company. The company's prescription drug is sold or distributed by the company using only the exclusive computer database of the company. The control of this embodiment exerted by the presence of the company's exclusive computer database further lends to the prevention of any potential abuse, misuse, and/or diversion of the prescription drug. The exclusive computer database of the company that obtained approval for distribution of the prescription drug is the only database in existence for the company's prescription drug, such that all prescriptions for the company's prescription drug are processed only by the exclusive computer database of the company.

In yet another embodiment wherein the single computer database is a single computer database of a company that obtained approval for distribution of the prescription drug, the prescription fields store all prescription requests, for all patients being prescribed the company's prescription drug, only in the single computer database of the company, from all physicians or other prescribers allowed to prescribe the company's prescription drug, such that all prescriptions for the company's prescription drug are processed using only the single computer database of the company (1211D).

In yet another embodiment, the exclusive computer database is associated with an exclusive central pharmacy, and not owned by the company that gained approval to distribute the prescription drug. In this situation, the inventory of the prescription drug is owned by the company, but the inventory is consigned to the exclusive central pharmacy and managed by the exclusive central pharmacy (1211E). This can be considered a hybrid embodiment.

As can be inferred and seen from the foregoing, a system to control the distribution of a prescription drug, which can be referred to as a Risk Evaluation and Mitigation Strategy (REMS) Program, has a goal of mitigating the risks of serious adverse outcomes resulting from inappropriate prescribing, misuse, abuse, and/or diversion of the prescription drug. This goal is achieved by (1) informing prescribers, pharmacists, patients, and caregivers of the risks, contraindications, potential for abuse, misuse, diversion, and/or overdose, and the safe use, handling, and storage of the prescription drug, and (2) ensuring that pharmacy controls exist prior to filling prescriptions that screen for concomitant use of potentially interacting agents, monitoring for inappropriate prescribing, and monitoring and notifying prescribers about concomitant use of contraindicated medications or signs of potential abuse, misuse, and/or diversion.

When prescribing prescription drugs, which have the potential for abuse, misuse, and/or diversion, to pediatric patients, caregivers are critical for many aspects of safe prescribing and use, even though such caregivers have not been considered formal stakeholders in prior pediatric programs. Nevertheless, as noted above, for pediatric patients, a distribution program includes a mandatory responsible adult caregiver as a condition of safe use for each patient. The pediatric REMS system ensures that caregivers of pediatric patients are counseled on the serious risks and safe use of the prescription drug. Medication guides and other material have information to ensure that these tools are relevant to both adult and pediatric patient groups. Counseling and attestation forms and other resources such as the quick start guide, medication guide, and caregiver brochure are also helpful for caregivers. Finally, certain central certified pharmacy material, training, and processes ensures the consistent implementation of a pediatric REMS program for all pediatric patients.

A responsible adult caregiver can be critical for many aspects of safe prescribing of sensitive drugs and use in pediatric patients (or elderly or other special needs patients). To implement this, caregivers should be included as formal stakeholders of a REMS Program. Several features are useful in making a caregiver a formal stakeholder. Prescribers and pharmacists should be formally required to counsel caregivers. If such counseling is not required, caregivers will not be apprised of the serious risks, how to safely use a prescription drug, how to safely handle a prescription drug, and how to safely store a prescription drug prior to initiating therapy.

Also, caregivers should formally be required to maintain responsibility for aspects of the safe prescribing, use, handling, and storage of the prescription drug, so that such caregivers can consistently maintain responsibility for these aspects. These responsibilities include notifying healthcare professionals immediately of possible serious adverse reactions associated with the prescription drug, ensuring compliance with contraindications (for example, alcohol and sedative hypnotics) and avoidance of concomitant use of the prescription drug with other potentially interacting agents, adherence to preparation and dosing instructions, adherence to not allowing a pediatric patient (or elderly or other special needs patient) to operate hazardous machinery, including automobiles, for a specified time period after taking a dose of the prescription drug until the caregiver knows how the prescription drug affects the patient, and adhering to safe use, handling, and storage procedures for the prescription drug. It should be noted, that in an embodiment, caregivers are required to educate each adult who may be assigned caregiver responsibilities, so that there is a consistency in educating each adult who may be assigned temporary responsibility (interim caregiver) for one or more components of safe use procedures (for example, the preparation, administration, safe use, handling, and storage of the prescription drug).

When prescriptions come into the exclusive central pharmacy, central certified pharmacy personnel can remind the prescribers that one has to be properly certified to write a prescription for the prescription drug. That is, the prescriber can be reminded by the central pharmacy personnel that the prescriber must have been properly educated on the pertinent REMS program requirements as they relate to the pediatric population.

The central certified pharmacy personnel should consistently ensure that the prescription drug is dispensed only to pediatric patients with an associated responsible adult caregiver who has been counseled on the serious risks and safe use of the prescription drug. Central certified pharmacy personnel should have official material and processes regarding dispensing the prescription drug to pediatric patients and should be trained on informal processes that have evolved for dispensing the prescription drug to pediatric patients. A central certified pharmacy patient/caregiver counseling checklist should adequately and consistently achieve its objectives in the pediatric population—that is proper education, distribution, storage, and usage of the prescription drug in the patient population.

In summary, an embodiment of a pediatric REMS program ensures that the prescription drug is shipped only to pediatric patients enrolled in the REMS program, and only to those pediatric patients with an associated caregiver with documented counseling and attestations. An exclusive central database includes REMS program caregiver counseling and attestation forms and REMS program patient/caregiver counseling checklists.

Another embodiment of the present drug distribution system includes the use of a device to facilitate the administration and tracking of a medication. For example, U.S. Pat. No. 9,801,852, which is incorporated herein by reference, discloses a dispensing device that facilitates and controls the use of a medication. The medication facilitated and controlled by the dispensing device can be in liquid or solid form. The present drug distribution system may facilitate controlled distribution of the dispensing device coupled with detection of the proper use of the medication by the authorized patient. The device allows for accurate dispensing of a medication, such as oxybate, under controlled conditions. In some embodiments there are optional features that can enhance the secure distribution or administration of the medication. In one embodiment, the dispenser is used with a medication, such as oxybate, without any additional security features, like a formulation change with an aversive for example.

A dispensing device, such as the device disclosed in U.S. Pat. No. 9,801,852, can include two compartments. A first compartment can include a product bag configured to hold the product (medication or prescription drug) and a treatment stack configured to treat the product. A second compartment can include a treatment reservoir configured to hold the treated product, a water reservoir configured to retain/supply water for dilution, a mixer configured to generate a diluted dose of the treated product, and a dilution vessel configured to hold the diluted product. The second compartment can additionally include a dose receiver for receiving a dose of the diluted product. In another embodiment, the first compartment simply holds multiple doses of the product, and the second compartment is configured to receive a single dosage of the product from the first compartment and make the single dosage available to a patient.

The dispensing device can also include a controller configured to control operation of the dispensing device. In some embodiments, the controller can include at least a processor and a memory. The controller can further include an input/output interface I/O that can encompass, but is not limited to, interfaces for network connectivity (wired/wireless, including Bluetooth), a display unit, input interfaces (such as selectable keys, a touchscreen, a control panel, and/or the like) for use by the user, and/or the like.

In some embodiments, the controller can optionally include a database for storing information including, but not limited to, patient information, dosing information, compliance information, and/or the like. In some embodiments, the controller can optionally include one or more locks to limit access to and/or use of the dispensing device. The locks can encompass hardware-based lockout mechanisms (e.g., a physical lock, a coded latch, and/or the like) as well as software-based lockout approaches (e.g., password and/or pin-based authentication) in some embodiments, the controller can optionally include one or more indicators for communicating with a user such as, for example a visual indicator (e.g., an LED), an audible indicator (e.g., a beeping sound), a graphic indicator (e.g., an icon), and/or the like. It is understood that the various illustrated components of the controller need not be mutually exclusive: for example, the lock can include password-based authentication that is based on instructions stored in the memory and executed by the processor.

In an embodiment, the processor of the dispenser can communicate with a REMS (Risk Evaluation and Management Strategy) system such as via the computer system 100 of FIG. 1, the eBook of FIG. 13, and/or some other component of a REMS system. This exchange can include the REMS system logging any data captured by the dispenser, and the dispenser storing any data and/or executing any instructions from the REMS system. The communication can also include a registration of the drug dispensing device by the patient, and a tracking of usage of the drug dispensing device by the patient, thereby also tracking usage of prescription drug by the patient.

For example, the REMS computer system 100 of FIG. 1 could transmit signals to the dispenser to control any locking mechanism on the dispenser (thereby controlling when a dose can be administered), prescription and/or dosing information that can be stored in the memory or database of the dispenser, and/or control the indicator of the dispenser. Similarly, the dispenser could transmit to the REMS computer system 100 of FIG. 1 when the locking mechanism is engaged or disengaged, and/or when a dosage is prepared and/or dispensed. Additionally, the REMS system and the dispenser can communicate regarding prescription refills of the dispenser. For example, the REMS system can communicate to the dispenser that a patient should be refilling the dispenser within a particular time period, perhaps in a day or two. Thereafter, sensors in the dispenser can transmit a signal back to the REMS when the dispenser is refilled. Such sensors can include a sensor that detects the full weight of a new prescription refill, a signal that a compartment that contains the prescription has been opened and then closed, etc. The dispenser can also transmit to the REMS system that a refill has not been added to the dispenser, such as after the time period in which the REMS system informed the dispenser that a refill should have been added. As another example, the dispenser may have a scale or other sensing device, and the sensor can signal to the REMS system that a refill will soon be needed. The REMS system can then check its database to determine if such a refill would be too soon, and an investigation could be launched to look into the reasons why the dispenser is unexpectedly low on the prescription.

More specifically, in connection with controlling access to dosages and/or monitoring refills, the REMS system can transmit to the processor and the database of the dispenser the dates and times of day during which a dosage can be made available, and cause the indicator to become illuminated signaling to a patient that a dose can be prepared, received, and/or administered. This programming can be implemented by the prescriber, and can be modified as need be (such as after a doctor office visit or after a patient has spilled or lost a prescription). This programming assures that the pharmaceutical is made ready for consumption only, when a patient is supposed to take the pharmaceutical. Likewise, the dispenser can communicate back to the REMS system a confirmation that the pharmaceutical has been properly removed from the dispenser.

The pharmaceutical can be stored in an internal reservoir of the dispenser and await usage by the patient. In an embodiment, the REMS system and/or the dispenser processor can control when a dosage is removed from the product container and placed in the internal reservoir for access by the patient. This internal reservoir can be secured by a physical lock, such as an electromagnetic lock, and this electromagnetic lock can be controlled by the dispenser processor and/or the REMS processor 100. If controlled by the dispenser processor, data relating to the access of the pharmaceutical can be transmitted to and stored in the REMS system. The communication between the REMS system and the dispenser is preferably via wireless means, but can also occur via wired means (such as over telephone lines).

In an embodiment, an aversive or other objectionable compound can be added to the pharmaceutical and the dispenser can remove the objectionable compound before the pharmaceutical is ingested by the patient. The presence of an aversive in the pharmaceutical helps prevent abuse or misuse of the pharmaceutical.

The data that can be exchanged between the REMS system and the dispenser can relate to one or more of the following—information displayed on a REMS or dispenser display unit; information input into the dispenser by a patient; the number of doses taken per time period, the time for the next dose; and the actual time of dosage; data relating to any manual override of some control features of the dispenser (such as allowing for dispensing multiple doses for travel); the functioning of an indicator light on the dispenser that a lockout period has lapsed and that another dose can be dispensed; an alarm to wake the patient for a second dose administration; passive authentication such as with infrared emitting diode on a bracelet worn by the patient; active authentication such as with a pincode entered by the patient; accessing a keyed enclosure to the product; programming controls that govern frequency and amount of administration and dispensing events; indicators displaying amount of drug treated, dispensed, and/or remaining within the dispenser; programming changes either by plug-in chip or cartridge or by remote connection such as a wireless device; a service life timer or performance measurement and indicator that may prompt the patient to either send the unit for service or replace consumable elements such as filters; distribution of fluids from the different reservoirs; the amount of fluid from each reservoir; changes to the amount of each dose; and balance (e.g., weight of product remaining and/or dispensed) information when a pharmaceutical is measured out by the dispenser.

It should be understood that there exist implementations of other variations and modifications of the invention and its various aspects, as may be readily apparent, for example, to those of ordinary skill in the art, and that the invention is not limited by specific embodiments described herein. Features and embodiments described above may be combined with each other in different combinations. It is therefore contemplated to cover any and all modifications, variations, combinations or equivalents that fall within the scope of the present invention.

The Abstract is provided to comply with 37 C.F.R. § 1.72(b) and will allow the reader to quickly ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.

In the foregoing description of the embodiments, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting that the claimed embodiments have more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate example embodiment. 

1. A computer-implemented system for distribution of a prescription drug that has a potential for abuse, misuse, or diversion, comprising: one or more computer memories for storing a central computer database and for receiving prescriptions from any and all patients being prescribed the prescription drug, said central computer database having a database schema that contains and interrelates prescription fields, patient fields, caregiver fields, and prescriber fields; said central computer database being distributed over multiple computers; said prescription fields, contained within the database schema, storing prescriptions for the prescription drug with the potential for abuse, misuse, or diversion; said patient fields, contained within the database schema, storing information sufficient to identify a patient for whom the prescription drug is prescribed; said caregiver fields, contained within the database schema, storing information sufficient to identify a caregiver associated with the patient; said prescriber fields, contained within the database schema, storing information sufficient to identify any and all physicians or other prescribers of the prescription drug and information to show that the physicians or other prescribers are authorized to prescribe the prescription drug; one or more data processors for processing one or more database queries that operate over data related to the prescription fields, prescriber fields, patient fields, and caregiver fields; said one or more database queries checking for abuse, misuse, or diversion within the central computer database, wherein the filling of the prescriptions is authorized for the prescription drug only if there is no record of incidents that indicate abuse, misuse, or diversion by the patient, caregiver, or prescriber, and if there is a record of such incidents, the central computer database indicates that such incidents have been investigated, and the central computer database indicates that such incidents do not involve abuse, misuse or diversion.
 2. The computer-implemented system of claim 1, wherein the prescription drug is sold or distributed by a company that obtained approval for distribution of the prescription drug.
 3. The computer-implemented system of claim 1, wherein the one or more database queries are processed by the one or more data processors for identifying that the patient or the caregiver associated with the patient is a cash payer and for identifying a physician that is interrelated with the patient through the schema of the single computer database; and wherein said identifying that the patient or the caregiver associated with the patient is a cash payer indicates potential abuse, misuse, or diversion by the patient or the caregiver associated with the patient and is used to notify the physician that is interrelated with the patient through the schema of the single computer database.
 4. The computer-implemented system of claim 1, wherein the one or more database queries operate over all data relating to said prescription fields, prescriber fields, patient fields, and caregiver fields over the multiple computers.
 5. The computer-implemented system of claim 1, wherein the central computer database is used to identify a current pattern or an anticipated pattern of abuse, misuse; or diversion of the prescription drug; and wherein the current pattern or the anticipated pattern is identified using periodic reports generated on a regular basis from the central computer database.
 6. The computer-implemented system of claim 1, wherein current inventory is cycle counted and reconciled with database quantities before shipments for a day or other time period are sent.
 7. The computer-implemented system of claim 1, wherein the one or more data processors are operable to communicate with a computer processor of a drug dispensing device, and wherein the one or more data processors and the computer processor of the drug dispensing device exchange data relating to the prescriptions, the prescription drug, the patient, the caregiver, the physicians, the prescribers, prescription refills, and the one or more database queries relating to the abuse, misuse, or diversion.
 8. The computer-implemented system of claim 7, wherein the communication from the one or more data processors comprises a signal to control a locking mechanism on the drug dispensing device.
 9. The computer-implemented system of claim 7, wherein the communication from the one or more data processors comprises dosing information that can be stored in the dispenser.
 10. The computer-implemented system of claim 7, wherein the communication from the one or more data processors comprises a signal to control an indicator on the drug dispensing device.
 11. The computer-implemented system of claim 7, wherein the communication from the one or more data processors comprises a signal to control removal of an objectionable compound from the prescription drug by the drug dispensing device, including one or more of a date and a time of day during which the objectionable compound can be removed from the prescription drug.
 12. The computer-implemented system of claim 7, wherein the communication from the one or more data processors comprises a signal to control when a dose can be removed from the drug dispensing device.
 13. The computer-implemented system of claim 7, wherein the communication from the one or more data processors comprises a signal to control an alarm associated with the drug dispensing device to signal to the patient that it is time to take a second dosage of the prescription drug.
 14. The computer-implemented system of claim 7, wherein the communication from the one or more data processors relates to a registration of the drug dispensing device by the patient, and a tracking of usage of the drug dispensing device by the patient.
 15. The computer-implemented system of claim 1, wherein the one or more database queries determine that the patient is not associated with any caregiver, or that the patient is no longer associated with any caregiver; and preventing shipment of the prescription drug to the patient based on the determination.
 16. The computer-implemented system of claim 15, wherein the one or more database queries access the central computer database to determine if the patient has transitioned to a new caregiver; and restarting shipments to the patient when the patient has transitioned to the new caregiver.
 17. The computer-implemented system of claim 1, wherein the one or more database queries selectively block shipment of the prescription drug to the patient and the caregiver associated with the patient based on a determination of potential abuse by the patient or the caregiver associated with the patient.
 18. The computer-implemented system of claim 1, wherein the patient and the caregiver associated with the patient are residents of a same household, and wherein the computer processor associates potential abuse of the prescription drug with the same household.
 19. The computer-implemented system of claim 1, wherein the one or more database queries determine that potential abuse is associated with a formulation from a brand manufacturer or a formulation from a generic manufacturer.
 20. The computer-implemented system of claim 1, wherein the one or more database queries probe the caregiver fields associated with the caregiver associated with the patient upon a refill request, and counseling the caregiver associated with the patient, or other contact with the caregiver associated with the patient, to verify that the caregiver associated with the patient is still acting as the caregiver for the patient; and when the caregiver associated with the patient is no longer acting as the caregiver for the patient, selecting a new caregiver for the patient before the refill is filled. 